Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarification about leftover change #10

Merged
merged 2 commits into from
Aug 26, 2019
Merged

Clarification about leftover change #10

merged 2 commits into from
Aug 26, 2019

Conversation

Siko91
Copy link

@Siko91 Siko91 commented Aug 26, 2019

Added clarification about creating extra outputs and not just the ones requested.

// Just clarifying that having more outputs than the requested ones is OK.
// ...It is OK, isn't it?

@ryanxcharles
Copy link

It an add other outputs for other reasons too, not just change.

@ryanxcharles
Copy link

Also that line should have "PaymentDetails" changed to "PaymentRequest". We took out PaymentDetails.

@Siko91
Copy link
Author

Siko91 commented Aug 26, 2019

I see... In that case how about something like:

Creates and signs a transaction that satisfy (pay in full) PaymentRequest.outputs. It may add additional outputs if needed.

@ryanxcharles
Copy link

That makes sense. Again, "PaymentDetails" should be "PaymentRequest".

@Siko91
Copy link
Author

Siko91 commented Aug 26, 2019

yes - comment fixed

@ryanxcharles ryanxcharles merged commit b74c8a8 into moneybutton:master Aug 26, 2019
@ryanxcharles
Copy link

Merged. Another relevant comment, though: It's actually unclear what the order of the outputs should be. Inside MB, we sort the outputs for increased privacy. This means the outputs are NOT returned in the same order. Perhaps we should clarify whether they should or should not be in the same order.

@Siko91
Copy link
Author

Siko91 commented Aug 26, 2019

Clarification would be good.
I believe that the better choice would be to not enforce any order.

It is technically possible to satisfy 2 payment requests with 1 transaction (and send that transaction to 2 different servers). Both are gonna find their inputs in it, but it is not possible for both to get the ordering they expected.

// though... I have no idea why anyone would do something like that. :D

@Siko91
Copy link
Author

Siko91 commented Aug 26, 2019

deleting this branch.

@Siko91 Siko91 deleted the patch-4 branch August 26, 2019 14:53
@ryanxcharles
Copy link

on output ordering, i created a new PR: #11

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants